This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@chat-adapter/teams@4.35.0

Minor Changes

• 46681f5: Expose Microsoft Graph email addresses on normalized incoming Teams message authors. Resolved user profiles are cached in the state adapter (1 hour, failed lookups 5 minutes) so the lookup doesn't add a Graph call per message.

Patch Changes

• 3895ab3: Fall back to Microsoft Graph's user principal name when a Teams user has no mail address.
• 93a58af: Show explicitly configured progress as a native Teams DM status while preserving native streaming.
• Updated dependencies [80def3a]
• Updated dependencies [46681f5]
• Updated dependencies [93a58af]
  • chat@4.35.0
  • @chat-adapter/shared@4.35.0

chat@4.35.0

Minor Changes

• 46681f5: Expose Microsoft Graph email addresses on normalized incoming Teams message authors. Resolved user profiles are cached in the state adapter (1 hour, failed lookups 5 minutes) so the lookup doesn't add a Graph call per message.

Patch Changes

• 80def3a: Add optional isSystem field to the normalized message Author type to distinguish platform-generated messages from humans and bots. The Slack adapter now sets isSystem: true for messages authored by Slack's reserved USLACK user (e.g. "@user archived the channel" notifications in DMs), so consumers no longer need to hard-code Slack-specific user IDs.
• 93a58af: Show explicitly configured progress as a native Teams DM status while preserving native streaming.

@chat-adapter/discord@4.35.0

Patch Changes

• Updated dependencies [80def3a]
• Updated dependencies [46681f5]
• Updated dependencies [93a58af]
  • chat@4.35.0
  • @chat-adapter/shared@4.35.0

@chat-adapter/gchat@4.35.0

Patch Changes

• 270b1c2: fix(gchat): accept endpointUrl as a direct-webhook verifier and verify each token type correctly

  When a Google Chat app's connection setting Authentication audience is set
  to HTTP endpoint URL — Google's recommended option for HTTP-hosted apps
  not behind Cloud Run IAM, and the only mode available for Workspace Add-on
  Chat apps — incoming tokens are Google OIDC ID tokens whose aud is the
  endpoint URL rather than the GCP project number. Previously the adapter only
  verified against googleChatProjectNumber, so URL-audience tokens always
  failed with 401 Unauthorized. The adapter now accepts endpointUrl as a
  direct-webhook verifier (including in the constructor's fail-closed check),
  validating the OIDC token's audience plus the Google Chat issuer email claims
  (chat@system.gserviceaccount.com, or the
  service-{projectNumber}@gcp-sa-gsuiteaddons.iam.gserviceaccount.com service
  identity for Workspace Add-on Chat apps) with email_verified: true — a
  public endpoint URL audience alone is not sufficient to forge a request.

  Project-number-audience tokens are now verified per Google's reference
  implementation: they are JWTs self-signed by
  chat@system.gserviceaccount.com, so the adapter checks them against that
  service account's X.509 certificates with issuer
  chat@system.gserviceaccount.com (previously it used verifyIdToken, which
  only accepts Google OIDC issuers and certs and therefore rejected every real
  project-number token). When both verifiers are configured, either token type
  is accepted.

  The adapter still infers an endpoint URL from incoming requests for
  button-click action routing only — that inferred value is never used as a
  JWT verification audience, and inference now only happens after a request
  has passed verification (or verification was explicitly disabled), because
  request.url derives from the attacker-controllable Host header in
  serverless runtimes.

• Updated dependencies [80def3a]

• Updated dependencies [46681f5]

• Updated dependencies [93a58af]

  • chat@4.35.0
  • @chat-adapter/shared@4.35.0

@chat-adapter/github@4.35.0

Patch Changes

• Updated dependencies [80def3a]
• Updated dependencies [46681f5]
• Updated dependencies [93a58af]
  • chat@4.35.0
  • @chat-adapter/shared@4.35.0

@chat-adapter/linear@4.35.0

Patch Changes

• Updated dependencies [80def3a]
• Updated dependencies [46681f5]
• Updated dependencies [93a58af]
  • chat@4.35.0
  • @chat-adapter/shared@4.35.0

@chat-adapter/messenger@4.35.0

Patch Changes

• Updated dependencies [80def3a]
• Updated dependencies [46681f5]
• Updated dependencies [93a58af]
  • chat@4.35.0
  • @chat-adapter/shared@4.35.0

@chat-adapter/shared@4.35.0

Patch Changes

• Updated dependencies [80def3a]
• Updated dependencies [46681f5]
• Updated dependencies [93a58af]
  • chat@4.35.0

@chat-adapter/slack@4.35.0

Patch Changes

• 80def3a: Add optional isSystem field to the normalized message Author type to distinguish platform-generated messages from humans and bots. The Slack adapter now sets isSystem: true for messages authored by Slack's reserved USLACK user (e.g. "@user archived the channel" notifications in DMs), so consumers no longer need to hard-code Slack-specific user IDs.
• Updated dependencies [80def3a]
• Updated dependencies [46681f5]
• Updated dependencies [93a58af]
  • chat@4.35.0
  • @chat-adapter/shared@4.35.0

@chat-adapter/telegram@4.35.0

Patch Changes

• 0701679: Cache the compiled bot-mention regex in isBotMentioned instead of recompiling it per message, and make the protected sleep helper accept an optional AbortSignal so stopPolling() interrupts the polling backoff delay immediately.
• Updated dependencies [80def3a]
• Updated dependencies [46681f5]
• Updated dependencies [93a58af]
  • chat@4.35.0
  • @chat-adapter/shared@4.35.0

@chat-adapter/twilio@4.35.0

Patch Changes

• Updated dependencies [80def3a]
• Updated dependencies [46681f5]
• Updated dependencies [93a58af]
  • chat@4.35.0
  • @chat-adapter/shared@4.35.0

@chat-adapter/web@4.35.0

Patch Changes

• Updated dependencies [80def3a]
• Updated dependencies [46681f5]
• Updated dependencies [93a58af]
  • chat@4.35.0
  • @chat-adapter/shared@4.35.0

@chat-adapter/whatsapp@4.35.0

Patch Changes

• Updated dependencies [80def3a]
• Updated dependencies [46681f5]
• Updated dependencies [93a58af]
  • chat@4.35.0
  • @chat-adapter/shared@4.35.0

@chat-adapter/x@4.35.0

Patch Changes

• Updated dependencies [80def3a]
• Updated dependencies [46681f5]
• Updated dependencies [93a58af]
  • chat@4.35.0
  • @chat-adapter/shared@4.35.0

@chat-adapter/state-ioredis@4.35.0

Patch Changes

• Updated dependencies [80def3a]
• Updated dependencies [46681f5]
• Updated dependencies [93a58af]
  • chat@4.35.0

@chat-adapter/state-memory@4.35.0

Patch Changes

• Updated dependencies [80def3a]
• Updated dependencies [46681f5]
• Updated dependencies [93a58af]
  • chat@4.35.0

@chat-adapter/state-pg@4.35.0

Patch Changes

• d88789c: Fix setIfNotExists() so it can claim a cache key whose existing row has expired. Previously the query used ON CONFLICT DO NOTHING, so an expired row in chat_state_cache still blocked acquisition until opportunistic cleanup deleted it — diverging from the memory and Redis adapters, which treat expired entries as absent. Keys stored without a TTL remain permanent and are never overwritten.
• Updated dependencies [80def3a]
• Updated dependencies [46681f5]
• Updated dependencies [93a58af]
  • chat@4.35.0

@chat-adapter/state-redis@4.35.0

Patch Changes

• Updated dependencies [80def3a]
• Updated dependencies [46681f5]
• Updated dependencies [93a58af]
  • chat@4.35.0

@chat-adapter/tests@4.35.0